Thanks @AlexanderKanakis

2 small things please...

• Is it possible to put the new config items at the top of the list in the UI, instead of at the bottom. I'm thinking that the choice of ES vs. CX should be topmost config.
• Can you indicate please in a comment on these fields that they are required for ES only?
  
  Thanks.

e

Also..... is this a typo? Not sure it makes sense to have this labeled [CX ONLY] and to suggest that it's not for CX.... :-)

Dialogflow CX does not use fallback events. This setting lists events that will be treated AS fallbacks by our Apps.Dialogflow. I can change the description and label to make this more clear.

@AlexanderKanakis How does authentication work? thanks

"Agent Version" at the top.... toggles between ES/CX

• CX Settings
  • CX only settings under this heading
• ES Settings
  • ES only settings under this heading
• General Settings
  • All the common settings under this heading

Thoughts?

Thanks @AlexanderKanakis

2 small things please...

* Is it possible to put the new config items at the top of the list in the UI, instead of at the bottom.  I'm thinking that the choice of ES vs. CX should be topmost config.

* Can you indicate please in a comment on these fields that they are required for ES only?
  ![image](https://user-images.githubusercontent.com/28864717/118545620-d4b0e300-b724-11eb-855e-b07acd9312ad.png)
  Thanks.

e

All of these settings are necessary for CX as well. There are only some CX exclusive.

@AlexanderKanakis How does authentication work? thanks

ES authenticates by sticking an access token as a URL parameter in its requests.
https://dialogflow.googleapis.com/v2/projects/${projectId}/agent/environments/${environment || 'draft'}/users/-/sessions/${sessionId}:detectIntent?access_token=${accessToken}

CX authenticates by placing the access token in the request's header.

{ 'Content-Type': Headers.CONTENT_TYPE_JSON, 'Accept': Headers.ACCEPT_JSON, 'Authorization': 'Bearer ' + accessToken },
   { queryInput },
);```

How do we configure the authentication token in CX? For ES there is an input box, do we need something similar for CX?

The authentication token in ES is configured with the private key and the client email. We get the authentication token in CX in the exact same way.

EDIT: It occured to me that the ES and CX agent might not be part of the same service as it is in my case. I will add the same fields (project id, client email, private key) as an optional input for CX, just in case the two agents are not part of the same service.

Ah, cool..... thanks. I think we can make some UI improvements here, and you probably saw the story I created about it. Let me know what you think. thanks.

Dialogflow CX does not use fallback events

Lets discus at standup, but I dont think we want the RC DF app doing an conversation manipulation

@Shailesh351 please review when you can....... thanks!

Functionally this PR Looks good to me. Nice work @AlexanderKanakis tada

I found that there are lint in some files. We have tslint configured in the project. You can use it for fixing lint issues.

Thanks!

Issues resolved in new commit!

Thanks @AlexanderKanakis @Shailesh351 !